Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: remoteImageSrc to come from resolved source #5867

Merged
merged 1 commit into from
Oct 18, 2024
Merged

Conversation

Palanikannan1437
Copy link
Collaborator

@Palanikannan1437 Palanikannan1437 commented Oct 18, 2024

Summary by CodeRabbit

  • New Features

    • Simplified handling of image attributes in the Custom Image Block, focusing on width, height, and aspect ratio.
  • Bug Fixes

    • Adjusted conditions for image loading and rendering to ensure proper functionality without the src attribute.

Copy link
Contributor

coderabbitai bot commented Oct 18, 2024

Walkthrough

The changes involve modifications to the CustomImageBlock component in the image-block.tsx file. The src attribute has been removed from the component's props, simplifying the handling of image attributes to focus on width, height, and aspectRatio. The handleImageLoad function has been updated to exclude the src from node.attrs, affecting the image loading process. Additionally, conditions related to image loader, utilities, and resizer have been adjusted to align with the new attribute structure, while maintaining the component's overall functionality.

Changes

File Path Change Summary
packages/editor/src/core/extensions/custom-image/components/image-block.tsx Removed src from destructured node.attrs and CustomImageBlockProps. Updated handleImageLoad and rendering logic to reflect changes.

Poem

In the garden of code, where images bloom,
A rabbit hops lightly, dispelling the gloom.
With width and height, the magic is spun,
No need for src, just let the fun run!
So here’s to the changes, so clever and bright,
A simpler path forward, a joyful delight! 🐇✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 81550ab and 123da2a.

📒 Files selected for processing (1)
  • packages/editor/src/core/extensions/custom-image/components/image-block.tsx (1 hunks)
🧰 Additional context used
🔇 Additional comments (4)
packages/editor/src/core/extensions/custom-image/components/image-block.tsx (4)

Line range hint 1-324: Summary of changes and recommendations.

The changes in this file successfully implement the PR objective of using a resolved source for the image. The removal of src from the component's props and the subsequent adjustments to the component's logic are well-executed. The fallback mechanism for displaying images is a good approach.

To ensure the changes are fully integrated:

  1. Verify that remoteImageSrc is correctly passed to the CustomImageBlock component where it's used.
  2. Check that imageFromFileSystem is properly handled in the parent components.
  3. Ensure that no references to node.attrs.src remain in this file.

These verifications will help maintain the integrity of the image handling throughout the codebase.


Line range hint 239-240: Approve image source handling with fallback.

The use of displayedImageSrc as remoteImageSrc || imageFromFileSystem for the img element's src attribute is a good approach. It allows for fallback to imageFromFileSystem when remoteImageSrc is not available, maintaining the ability to display both remote and local images.

Let's verify the imageFromFileSystem prop is correctly passed to the component:

#!/bin/bash
# Search for the usage of CustomImageBlock component to check imageFromFileSystem prop
rg 'CustomImageBlock.*imageFromFileSystem' packages/editor/src

Also applies to: 254-255


Line range hint 232-238: Approve updated conditions for UI element visibility.

The changes to showImageLoader, showImageUtils, and showImageResizer conditions are consistent with the removal of src from the component's props. The use of remoteImageSrc maintains the same logic while aligning with the PR objective.

Let's verify the remoteImageSrc prop is correctly passed to the component:

#!/bin/bash
# Search for the usage of CustomImageBlock component to check remoteImageSrc prop
rg 'CustomImageBlock.*remoteImageSrc' packages/editor/src

62-62: Approve removal of src from destructured node.attrs.

This change aligns with the PR objective and simplifies the component's attribute handling. However, we should verify that the image source is correctly managed elsewhere in the component or by parent components.

To ensure the image source is correctly handled, let's check for any remaining references to node.attrs.src:


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants